NTISthis.com

Evidence Guide: ICAPRG413A - Use a library or pre-existing components

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICAPRG413A - Use a library or pre-existing components

What evidence can you provide to prove your understanding of each of the following citeria?

Identify potential reuse units

  1. Analyse project design and functionality to identify reuse components
  2. Source reuse components with desired functionality
Analyse project design and functionality to identify reuse components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Source reuse components with desired functionality

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate reuse components for suitability in parent project

  1. Evaluate reuse component or libraries for suitability for use within the parent software project
  2. Compare functionality of each potential reuse component to functionality required by parent project
  3. Evaluate cost of implementing reuse component
  4. Consider technical impact on parent project design
  5. Consider reuse component vendor licensing issues
  6. Finalise selection of reuse components
  7. Document selection, evaluation and decision processes as part of the parent project-design documentation
Evaluate reuse component or libraries for suitability for use within the parent software project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Compare functionality of each potential reuse component to functionality required by parent project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Evaluate cost of implementing reuse component

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider technical impact on parent project design

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Consider reuse component vendor licensing issues

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Finalise selection of reuse components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document selection, evaluation and decision processes as part of the parent project-design documentation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Incorporate reuse components

  1. Configure development environment to include reuse components during build process
  2. Construct test programs or use provided example programs to become familiar with reuse components in preparation for incorporation into parent project
  3. Add reuse components to parent project incrementally
  4. Resolve reuse component dependencies
  5. Assemble and test parent project with a focus on the functionality provided by reuse components
Configure development environment to include reuse components during build process

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Construct test programs or use provided example programs to become familiar with reuse components in preparation for incorporation into parent project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Add reuse components to parent project incrementally

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Resolve reuse component dependencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assemble and test parent project with a focus on the functionality provided by reuse components

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

meet project requirements by efficiently identifying, modifying and integrating components for reuse.

Context of and specific resources for assessment

Assessment must ensure access to:

software development environment

reuse library

technical requirements

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

verbal or written questioning to assess knowledge of the purpose of reuse libraries

review of the documentation when selecting a reuse component

evaluation of the completed program code incorporating the reuse library.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Required Skills and Knowledge

Required skills

analytical skills to:

analyse project design and functionality

evaluate reuse components

literacy skills to document selection, evaluation and decision processes

numeracy skills to evaluate cost of reusing components

planning and organisational skills to identify, analyse and evaluate a range of solutions

problem-solving skills to solve issues with the use of the library

research skills for identifying, analysing and evaluating broad features of current reuse issues and best practice in component reuse

technical skills to:

complete abstraction for a range of solutions

apply appropriate naming standards for a range of solutions.

Required knowledge

broad knowledge of:

contract specifications

current industry development and design methodologies

detailed knowledge of:

domain modelling

genericity specification

content and structure of libraries

techniques for metrics collection

patterns, frameworks and idioms

repository tools.

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Project may include:

business improvement process

business involved in a total organisational change

ebusiness solution involving the total organisation or part of the organisation

systems-only change.

Reuse components may include:

code

design patterns

metadata

requirements

specifications.

Documentation may follow:

audit trails

International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and Australian Standards (AS) standards

naming standards

project-management templates

report-writing protocols

version control.

Development environment may include:

computer language used

development methodology

development tools

operating systems

target environments

version control systems.